home *** CD-ROM | disk | FTP | other *** search
- Path: ar.ar.com.au!not-for-mail
- From: storm@ar.ar.com.au (Storm)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: One hardware-basher's manifesto
- Date: 29 Feb 1996 09:48:29 +1100
- Organization: I need to put my ORGANIZATION here.
- Message-ID: <4h2m3t$sd4@ar.ar.com.au>
- References: <4ge8na$vhe@ar.ar.com.au> <08000305729070351637@BIRDLAND> <4guenp$1a1@vixen.cso.uiuc.edu>
- NNTP-Posting-Host: ar.ar.com.au
- X-Newsreader: TIN [UNIX 1.3 941216BETA PL0]
-
- Saladino Michael D (msaladin@students.uiuc.edu) wrote:
- : >> : > Please use OwnBlitter/DisOwn... and use CacheControl to turn on only the caches
- : >> : > you need (If data burst (030/040/060) modes is on the CPU will take 4x as much
- : >> : > time when accessing fastram randomly.
-
- : I don't think I can express in words just how wrong this is, but I'm going to do my
- : best. First of all, even if you were accessing RAM "randomly", you will not suffer
- : a 4x speed drop. Checking a cache (L1 or L2) you only suffer a few clock cycles and
- : this is kept to a minimum thanks to pipelining the cache lookup hardware. However,
- : this is a moot point because programs don't access RAM randomly. The whole point
- : of the cache is to take advantage of the temporal and spatial locality that occurs
- : in ALL programs. You would actually have to go WAY out of your way to make a program
- : that runs faster with caches turned off and I bet it wouldn't do much. Are you aware
- : that modern day processors (and I'm even including the 680x0 line) get over 90% hit
- : rates on their data caches and even higher for the instruction cache. Turning a
- : cache off is like flipping a switch to drop your clock from 50Mhz to 5Mhz. It's
- : stupid... don't do it!
-
- Two points.
-
- #1 Format your post to 80 columns.. that was almost unreadable!
-
- #2 Nobody suggested killing CACHES.. he was talking about the DATA BURST mode,
- which fills the cache 4 (?) longwords at a time rather than 1 on an 030. Now,
- of course, killing the cache is a bad idea and it is indeed almost impossible
- to make something run slower with the cache on. But with the BURST mode on,
- and relatively random memory access (we'll pretend you never made that "programs
- don't access RAM randomly" generalisation), you will find yourself wasting time
- bursting 4 longwords into the cache instead of 1, when the other 3 will not
- be used (or probably not be used).
-
- Your reply is appreciated, but why do I get the impression that you just saw
- the words "cache" and "off" in the same sentence and unleashed a paragraph
- from a comp sci textbook, without actually checking what was being discussed?
-
- -- ______________________________
- \_/ "\/\/\__"\/ "\/ "\/\__"\_/
- Storm / Cydonia / / / / / / / / / / / / ' / Packing class
- / /\/> / / / / / / / / / /__ & kicking arse!
- (coder) \__/ \_/\__/\__/\/\/\/\/\/ \/
-
-